Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1051

reference
690-tree-1
name
1051
tree-preservation-order

undefined

690-tpo-1
uprn
address-text
point
POINT (-1.017462 50.882181)
geometry
MULTIPOLYGON (((-1.017406 50.882175,-1.017408 50.882186,-1.017416 50.882196,-1.017428 50.882204,-1.017444 50.882209,-1.017462 50.882211,-1.017479 50.882210,-1.017495 50.882205,-1.017508 50.882197,-1.017516 50.882187,-1.017519 50.882176,-1.017517 50.882165,-1.017509 50.882154,-1.017496 50.882146,-1.017481 50.882141,-1.017463 50.882139,-1.017446 50.882141,-1.017430 50.882146,-1.017417 50.882154,-1.017409 50.882164,-1.017406 50.882175)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL